This is G o o g l e's cache of http://www.rockbox.org/twiki/bin/view/Main/DevelopmentGuide as retrieved on 8 Sep 2005 04:31:12 GMT.
G o o g l e's cache is the snapshot that we took of the page as we crawled the web.
The page may have changed since that time. Click here for the current page without highlighting.
This cached page may reference images which are no longer available. Click here for the cached text only.
To link to or bookmark this page, use the following url: http://www.google.com/search?q=cache:wO7UTF3VAp4J:www.rockbox.org/twiki/bin/view/Main/DevelopmentGuide+site:rockbox.org+twiki+developmentguide&hl=en&client=firefox


Google is neither affiliated with the authors of this page nor responsible for its content.
These search terms have been highlighted: developmentguide 
These terms only appear in links pointing to this page: twiki

Rockbox . Main . DevelopmentGuide

 Rockbox Logo 

home
download
documentation
mailing lists
wiki
IRC
forums
daily builds
feature requests
bug reports
patches


SourceForge.net Logo

Rockbox > Main > DocsIndex > DevelopmentGuide
Main . { Users | Changes | Index | Search | Register | Go }

First Time Guide to Rockbox Development

Welcome to our humble project.

In order to get your hands dirty as quickly and smoothly as possible, here follows our suggested approach!

Join the Rockbox Community

Mail: We have a very active developers mailing list no serious Rockbox freak can live without.

IRC: There's always a bunch of friendly and helpful people around in the IRC channel.

Setup Your Environment

You need a cross-compiler and linker to build the code. Pick one of these:

Get The Source

Get a fresh source to build Rockbox from. We usually recommend you get the sources fresh from the CVS repo (How to use CVS), but you can also get a daily tarball or even the latest released source package.

Build Rockbox

Build rockbox using your acquired sources! If you're using Linux or the suggested cygwin approach, read How to compile Rockbox.

Also note that we have put a whole lot of effort in writing simulators so that you can build, run and try code on your host PC before you build and download your target version. This of course requires a working compiler for your native system.

Change Rockbox

Before you change any code, make sure to read the contributing information if you want to have any hope of having your changes accepted.

Now, you fixed any bugs? You added any features? Then make a patch and head over to the patch tracker and submit it. Of course, you can also check the open bugreports and jump in and fix one of them (or possibly submit a new bug report).

Regularly checking the open feature requests gives a picture of what people want to see happen and what is left to add...

You'll be better off with a sourceforge account for most bugreport and feature-request work.


CategoryHowto: First-time guide to Rockbox development

{ Edit | View raw | Attach | Ref-By | Printable | Diffs | r1.7 | > | r1.6 | > | r1.5 | More }
Revision r1.7 - 31 Aug 2005 - 08:03 GMT - LinusNielsenFeltzing
Parents: DocsIndex
Copyright © 1999-2005 by the contributing authors.